View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001466 | K18X001.00 SKB SWAN | SW | public | 2022-04-20 12:24 | 2025-07-17 17:07 |
| Reporter | (ALTech) Wooshin Kang | Assigned To | (ALTech) Wooshin Kang | Due Date | 2022-04-30 13:16 |
| Priority | normal | Severity | s6-feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0001466: Implement sending event to M/W when aux cable is detection. | ||||
| Description | Can you make below function ? "Please implement to deliver each event to M/W when aux is plug or unplug." And, inform us if you need something to implement it. < SKB JIRA > https://jira.skbroadband.com/browse/BTVD-21136 | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
|
|
Hi Wooshin, I have few questions about this requirement. 1.AUX cable plugin can be detected. But Audio Routing may not change to AUX path when AUX cable is plugged during NUGU Call and NUGU is running. So, I want to make sure if M/W only needs event when AUX plug and unplug? 2.There is no definition for how to send the event. Can we just set a property for AUX plug/unplug and M/W to check it? |
|
|
Hi River, I will contact skb and sptek and will share their opinion. Thanks. |
|
|
Hi River, SKB Manager requests to hold on this ticket If any update, i will contact again. Thanks. |
|
|
Hi River, We have to fill below function for AUX. add api : int AMIXER_setAUXInputMode(AMIXER_HANDLE amixer, int mode); add api : int AMIXER_GetAUXInputMode(AMIXER_HANDLE amixer, int *mode); add api : int AMIXER_GetAUXConnectionState(AMIXER_HANDLE amixer, int *state); add api : int AMIXER_SetAuxConnectionListener(AMIXER_HANDLE amixer, AMIXER_AuxConnectoinCallback callback); Please check below commit message. commit 1cab56fb12526d7c310e51b5f7d6355f5358dcb1 (HEAD -> BTF_API_LEVEL_6/bg5ct/ua300, soc-syna/BTF_API_LEVEL_6/bg5ct/ua300, m/BFX-UA300_5.3.4) Author: echwang <echwang@sptek.co.kr> Date: Fri Jun 3 19:59:54 2022 +0900 |
|
|
Hi Woohsin. First, we need to know, how Sptek will use these APIs. Because as you know in https://172.18.223.170/vaas/view.php?id=987, we ever has a mechanism to use properties to decide if we can swich to AUX-IN path with NUGU implementation. (This is beacuse reference audio for NUGU and AUX/Kaeaoke use a I2S switch and only one path can be selected at one time.). If no such mechanism, we can not open ALSA AUX sound card, because NUGU will always occupy it. So, please help to answer the following quesionts: 1.When AMIXER_setAUXInputMode() is called, what do we need to do? Do we still need to use property to communicate with NUGU to see if we can switch to AUX-IN or not? But if so, we can not know when AUX-IN will be switched because we need to polling property in a thread. 2.What is the value of mode in AMIXER_setAUXInputMode() and AMIXER_GetAUXInputMode()? 3.For AMIXER_GetAUXConnectionState(), do we need only show the AUX-IN cable plug status even we can not switch to AUX-IN Path? Please note: AUX-in Cable has two status: plug and unplug. But when it is plug, it does means AUX-IN path is configured, it needs to wait for NUGU to allow it. So, there is a status that AUX-IN is plugged but audio path is not change to AUX-in because NUGU is not free the sound card. For these APIs, they are not clear. Please answer the following questions: 1.What is the value of "mode" in AMIXER_SetAUXInputMode() and AMIXER_GetAUXInputMode()? Please describe each value of mode and the behavior thet want. 2.When will Sptek to call AMIXER_setAUXInputMode()? |
|
|
Actually, SKB want to control aux output by ui menu. And these api will be used by M/W. I think that these APIs and the properties currently being used should be properly linked. 1. When AMIXER_setAUXInputMode() is called, what do we need to do? -> It will be used aux output ON/OFF selection. 2.What is the value of mode in AMIXER_setAUXInputMode() and AMIXER_GetAUXInputMode()? -> 0 : output off, 1 : output on; 3.For AMIXER_GetAUXConnectionState(), do we need only show the AUX-IN cable plug status even we can not switch to AUX-IN Path? -> yes, I should be show connection status. About your note : UI will control aux path from this version by setting AMIXER_setAUXInputMode. SKB will inform to us about exact aux scenario after internal discussion. First, please fill API functions. Thanks |
|
|
Hi Wooshin, So, do you mean we still need to communicate with NUGU/NUGU CALL(by property) in our side not in UI side? Please see the attached file and confirm it is case 1 or case2. Because the API implementation needs to do different thing for these two cases. If case1 is chosen, then I have some quesions about AMIXER_SetAUXInputMode() and AMIXER_GetAUXInputMode(): 1.For AMIXER_SetAUXInputMode(), becaseu SetAUXInputMode() can not immediately take effect, for example NUGU Call is on running. Then, should we return this API immediately without return any error? Or block the API and wait until NUGU releases sound card and we can get Audio from AUX-in (please note UI may hang for waiting API blocking too long)? 2.Regarding AMIXER_GetAUXInputMode() in this case, does the input parameter "mode" just returns what AMIXER_SetAUXInputMode() set? or the "mode" returns the status of the audio path that really changes to AUX-in path(for example, before NUGU Call is still running, it return 0:output off, After NUGU Call release sound card and AUX-in audio path is switched, then we can return 1: output on.) Or just to return the status of AMIXER_SetAUXInputMode()? |
|
|
Hi River, So, do you mean we still need to communicate with NUGU/NUGU CALL(by property) in our side not in UI side? -> Yes, you have to communicate with NUGU/NUGU CALL in your side. If any changes in there, i will inform you. About 1, 2 question, I think you don't need to get answer if there is below limitation. When NUGU or NUGU call is working, ui can't call "AMIXER_SetAUXInputMode() or AMIXER_GetAUXInputMode()". Thanks. |
|
|
Hi Wooshin, About 1, 2 question, I think you don't need to get answer if there is below limitation. When NUGU or NUGU call is working, ui can't call "AMIXER_SetAUXInputMode() or AMIXER_GetAUXInputMode()". >> As I said, when UI is in AUX-IN setting, user can enable AUX-in, then UI will call AMIXER_SetAUXInputMode(). At the same time if the incomming NUGU Call is comming or NUGU button of RCU button is pressed. There are two situations: (1)NUGU/NUGU Call is running and the API check with NUGU process, NUGU does not set protperty. So, we needs to wait for NUGU/NUGU Call to be finished. So, there is a time duration, we can not immediate switch to AUX-in Path. That's why we ask quesiton 1 above. (2)API get the sound card from NUGU first. But then we found NUGU process ask us to release it (NUGU/NUGU CALL has higer priority then AUX-IN). So we need to set AUX-in path off to release sound card. For this case, we need to know how to reponse "mode" of AMIXER_GetAUXInputMode(). I think UI has to consider the NUGU/NUGU Call usage cases (for example, incoming NUGU Call), and then think they will how to use these APIs. Otherwise, it will cause some bugs in some special test cases and we needs spend more time to fix those bugs. |
|
|
Hi River, About 1, 2 question, I think you don't need to get answer if there is below limitation. When NUGU or NUGU call is working, ui can't call "AMIXER_SetAUXInputMode() or AMIXER_GetAUXInputMode()". >> As I said, when UI is in AUX-IN setting, user can enable AUX-in, then UI will call AMIXER_SetAUXInputMode(). At the same time if the incomming NUGU Call is comming or NUGU button of RCU button is pressed. [wooshin] Ignore this case at now. There are two situations: (1)NUGU/NUGU Call is running and the API check with NUGU process, NUGU does not set protperty. So, we needs to wait for NUGU/NUGU Call to be finished. So, there is a time duration, we can not immediate switch to AUX-in Path. That's why we ask quesiton 1 above. (2)API get the sound card from NUGU first. But then we found NUGU process ask us to release it (NUGU/NUGU CALL has higer priority then AUX-IN). So we need to set AUX-in path off to release sound card. For this case, we need to know how to reponse "mode" of AMIXER_GetAUXInputMode(). [wooshin] It should be returned "0" because aux path is already released. I think UI has to consider the NUGU/NUGU Call usage cases (for example, incoming NUGU Call), and then think they will how to use these APIs. Otherwise, it will cause some bugs in some special test cases and we needs spend more time to fix those bugs. [wooshin] I already told it to SKB, so they will discuss with UI engineer and will inform us about result. [wooshin] Firstly, Fill api function and then ui developer will check if there is any issue. [wooshin] Everything can't be perfect at once because we are working with several company, we have to go step by sep with debugging. |
|
|
Hi Wooshin, When will SKB plan to use this APIs? We need to know the schedule first. |
|
|
Hi River, I should be used from 534 version. 534 schedule is following. QA 6/16~7/13, BMT 7/14~8/10 So you have to work it ASAP. Thanks. |
|
|
Hi River, Are you working for it ? Thanks. |
|
|
Hi Wooshin, I am checking how to implement it. The AUX-IN code is complicated. I think it may take at least 2 weeks to have 1st version. |
|
|
Hi River, You have to commit it for ui development company ASAP. Please hurry up to implement it. Thanks. |
|
|
Hi Wooshin, I just commited the implementation to bitbucket. You can notify UI developer to test it. Please note, this commit will cause no audio when you plug in AUX-IN because it is now controlled by API. Another thing to remind, for speeding up this implement, We use property to implement APIs, so UI process need to has sepolicy permission to access "vendor.skb.btv." property. But I think it should not a problem because they should already add sepolicy for it. If UI developer still encounters some issue, we can help to check if there is sepolicy issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-04-20 12:24 | (ALTech) Wooshin Kang | New Issue | |
| 2022-04-20 12:24 | (ALTech) Wooshin Kang | Status | new => assigned |
| 2022-04-20 12:24 | (ALTech) Wooshin Kang | Assigned To | => (SW) River Wong |
| 2022-04-22 08:34 | (SW) Jacky Chiang | Severity | s2-severe => s6-feature |
| 2022-04-22 19:05 |
|
Note Added: 0009916 | |
| 2022-04-25 08:40 | (ALTech) Wooshin Kang | Note Added: 0009918 | |
| 2022-04-25 08:53 | (ALTech) Wooshin Kang | Note Added: 0009919 | |
| 2022-05-16 08:52 |
|
Assigned To | (SW) River Wong => (ALTech) Wooshin Kang |
| 2022-06-07 12:57 | (ALTech) Wooshin Kang | Note Added: 0010113 | |
| 2022-06-07 17:57 |
|
Note Added: 0010115 | |
| 2022-06-07 17:58 |
|
Note Edited: 0010115 | |
| 2022-06-07 17:59 |
|
Note Edited: 0010115 | |
| 2022-06-08 13:31 | (ALTech) Wooshin Kang | Note Added: 0010122 | |
| 2022-06-09 12:12 |
|
File Added: aux_cable_dection_API.pptx | |
| 2022-06-09 12:12 |
|
Note Added: 0010129 | |
| 2022-06-09 14:22 | (ALTech) Wooshin Kang | Note Added: 0010132 | |
| 2022-06-09 14:46 |
|
Note Added: 0010134 | |
| 2022-06-09 15:15 | (ALTech) Wooshin Kang | Note Added: 0010137 | |
| 2022-06-09 15:17 | (ALTech) Wooshin Kang | Note Edited: 0010137 | |
| 2022-06-09 15:19 | (ALTech) Wooshin Kang | Note Edited: 0010137 | |
| 2022-06-14 12:46 |
|
Note Added: 0010175 | |
| 2022-06-14 12:46 |
|
Note Edited: 0010175 | |
| 2022-06-14 13:31 | (ALTech) Wooshin Kang | Note Added: 0010177 | |
| 2022-06-15 09:28 | (ALTech) Wooshin Kang | Note Added: 0010181 | |
| 2022-06-15 13:36 |
|
Note Added: 0010182 | |
| 2022-06-20 15:41 | (ALTech) Wooshin Kang | Note Added: 0010210 | |
| 2022-06-22 11:33 |
|
Note Added: 0010227 | |
| 2025-07-17 17:07 | (PM) Sheila Tu | Status | assigned => closed |
| 2025-07-17 17:07 | (PM) Sheila Tu | Resolution | open => fixed |
